chore(deps): update docker/login-action action to v4.6.0 - #29

Dependency Bump Evaluation

Version change: v4.4.0 -> v4.5.2 (minor)
Breaking changes: None
Security concerns: None -- no CVEs, maintained by Docker (crazy-max)

Changes across 3 releases:

• v4.5.0: Docker Hub OIDC login support (new, opt-in), transitive dependency bumps
• v4.5.1: Support dhi.io as Docker Hub OIDC registry
• v4.5.2: Surface Docker Hub OIDC error responses

Impact on codebase: The action is used once in build.yaml for GHCR login with username/password auth. None of the OIDC-related changes affect this auth flow -- all new features are additive and opt-in.

CI status: build and generate passed; lint, test, test-e2e still in progress at time of evaluation.

Recommendation: SAFE TO MERGE (once CI is green)

Notes: Cannot auto-approve -- PR authored by renovate, not dependabot. Low-risk minor bump with only additive changes unrelated to the project's GHCR username/password login.

-- Claude Code

Dependency Bump Evaluation

Version change: docker/login-action v4.4.0 → v4.6.0 (minor)
Semver bump type: minor (spans 4 releases: v4.5.0, v4.5.1, v4.5.2, v4.6.0)

Changes:

• Docker Hub OIDC login support (v4.5.0) — new feature, additive
• Support dhi.io as Docker Hub OIDC registry (v4.5.1)
• Surface Docker Hub OIDC error responses (v4.5.2)
• Harden buildx scoped config path handling (v4.6.0) — security hardening
• Routine dependency bumps (aws-sdk, actions-toolkit, js-yaml, postcss, brace-expansion)

Breaking changes: None

Security concerns: None — v4.6.0 includes a positive security hardening for buildx config path handling. No CVEs or advisories.

Pin verification: Commit SHA dbcb813823bdd20940b903addbd779551569679f matches the v4.6.0 tag

Impact on codebase: This repo uses docker/login-action only for GHCR login with username/password credentials in .github/workflows/build.yaml. The new Docker Hub OIDC feature is not used. The config path hardening is a beneficial internal improvement. No code paths are affected by any of the changes.

CI status: Several checks still in progress at time of review (build, lint, test, test-e2e). Verify CI is green before merging.

Recommendation: SAFE TO MERGE (once CI passes)

— Claude Code